Method, system and apparatus for selectively obtaining map image data according to virtual camera velocity

ABSTRACT

Methods, systems and apparatus are described to selectively obtain map image data according to virtual camera velocity. Embodiments may display a map view of a map using a virtual camera. Some embodiments may detect a velocity of the virtual camera. Embodiments may then determine map image data for the map view of the map according to the velocity of the virtual camera and obtain the determined map image data. In at least some embodiments, a level-of-detail may be specified for map image data according to the velocity. Map image data may be obtained corresponding to this level-of-detail from a map service or from accessing local storage.

This application claims benefit of priority to U.S. ProvisionalApplication Ser. No. 61/655,831, entitled “Method, System And ApparatusFor Selectively Obtaining Map Image Data According To Virtual CameraVelocity,” filed Jun. 5, 2012.

BACKGROUND Description of the Related Art

Mobile computing is an expanding field of technological development.Advances in mobile communications, mobile hardware, and mobile softwareapplications are continually developing new solutions for existinglimitations in the field and providing innovative products forconsumers. As part of the growing demand for mobile softwareapplications, map displays and navigation applications provide a userwith various forms of maps, navigation, and direction information.Often, map image data is manipulated and displayed by mobile devices,such as mobile phones, personal digital assistants, tablet computers, orlaptop computers. Interactivity with these applications increases theprocessing demand on a mobile device which, if not accounted for, maylead to bad user experiences or application failure. To account for anapplication's demand on a mobile device's resources, applicationdesigners may attempt to reduce the size or quantity of transactionsnecessary to perform mobile software applications.

SUMMARY

Various embodiments of methods, apparatus, and computer-readable storagemedia for selectively obtaining map image data according to virtualcamera velocity are described. An electronic or computing device, suchas a laptop, desktop computer, mobile phone, personal digital assistant(PDA), portable multi-function device or tablet computer may implementselectively obtaining map image data according to virtual cameravelocity. Embodiments may implement a map application configured todisplay a map view of a map. Some embodiments may use a virtual camerafor a map view of a map, to determine map image data in the map view fortwo or three-dimensions. This virtual camera may be moved throughoutvirtual space to provide various views of the map image data. Usersand/or other input devices may move the virtual camera throughtouch-sensitive devices, orientation sensors, and location data. In someembodiments, a navigation system may provide continuous movement of avirtual camera along a route on a map. As the virtual camera moves, itsvelocity may be calculated. Embodiments may then determine map imagedata indicating a level-of-detail for the map image data, thelevel-of-detail is determined according to the velocity of the virtualcamera. In some embodiments, the distance between the virtual camera andthe observed map image data may specify the level-of-detail of map imagedata an embodiment may indicate. Embodiments may then obtain thedetermined map image data. Embodiments may obtain map image data from aserver, such as a map service, and/or by accessing locally stored mapimage data. Embodiments may then render the map image data. Someembodiments may then display the map image data to a viewer of a displaydevice, and/or store the image for further processing in local storageor by other applications.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a map service operating environment, according tosome embodiments.

FIG. 2 illustrates a flowchart for a method of selectively obtaining mapimage data according to virtual camera velocity, according to someembodiments.

FIGS. 3 a illustrates a virtual camera in virtual space as it observestwo-dimensional map image data, according to some embodiments.

FIG. 3 b illustrates a virtual camera in virtual space as it observesthree-dimensional map image data, according to some embodiments.

FIGS. 4 a and 4 b illustrate an example display of map data selectivelyobtained according to virtual camera velocity, according to someembodiments.

FIG. 5 illustrates the rotation of a virtual camera about a fixedposition and may illuminate how some embodiments detect virtual cameravelocity, according to some embodiments.

FIG. 6 a illustrates an example of touch input to a touch-sensitiveinput device and its effect upon the movement of a virtual camera,according to some embodiments.

FIG. 6 b illustrates an example of orientation sensor input and itseffect upon the movement of a virtual camera, according to someembodiments.

FIG. 6 c illustrates an example of location data and its effect upon themovement of a virtual camera, according to some embodiments.

FIGS. 7 a and 7 b illustrate differing levels of relative distance invirtual space from a virtual camera with varying level-of-detailspecified, according to some embodiments.

FIG. 8 illustrates a map module implementing a method to selectivelyobtain map data according to virtual camera velocity, according to someembodiments.

FIG. 9 illustrates an example electronic device, according to someembodiments.

FIG. 10 illustrates an example electronic device, according to someembodiments.

FIG. 11 illustrates an example electronic device, according to someembodiments.

FIG. 12 illustrates an example electronic device, according to someembodiments.

FIG. 13 illustrates an example system, according to some embodiments.

While the invention is described herein by way of example for severalembodiments and illustrative drawings, those skilled in the art willrecognize that the invention is not limited to the embodiments ordrawings described. It should be understood, that the drawings anddetailed description thereto are not intended to limit the invention tothe particular form disclosed, but on the contrary, the intention is tocover all modifications, equivalents and alternatives falling within thespirit and scope of the present invention. The headings used herein arefor organizational purposes only and are not meant to be used to limitthe scope of the description. As used throughout this application, theword “may” is used in a permissive sense (i.e., meaning having thepotential to), rather than the mandatory sense (i.e., meaning must).Similarly, the words “include”, “including”, and “includes” meanincluding, but not limited to.

DETAILED DESCRIPTION OF EMBODIMENTS

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, methods, apparatus, or systems that would be known by one ofordinary skill have not been described in detail so as not to obscureclaimed subject matter.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the scope of the present invention. Thefirst contact and the second contact are both contacts, but they are notthe same contact.

The terminology used in the description of the invention herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a”, “an” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “includes,” “including,”“comprises,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in response to detecting,” dependingon the context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” may be construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Some portions of the detailed description which follow are presented interms of algorithms or symbolic representation of operations on binarydigital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular functions pursuant to instructions from program software andother programmable electronic devices. Algorithmic descriptions orsymbolic representations are examples of techniques used by those ofordinary skill in the signal processing or related arts to convey thesubstance of their work to others skilled in the art. An algorithm ishere, and is generally, considered to be a self-consistent sequence ofoperations or similar signal processing leading to a desired result. Inthis context, operations or processing involve physical manipulation ofphysical quantities. Typically, although not necessarily, suchquantities may take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared or otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to such signals as bits, data, values,elements, symbols, characters, terms, numbers, numerals or the like. Itshould be understood, however, that all of these or similar terms are tobe associated with appropriate physical quantities and are merelyconvenient labels.

Various embodiments of methods, apparatus, and computer-readable storagemedia for selectively obtaining map image data according to virtualcamera velocity are described herein. Some embodiments may selectivelyobtain map image data according to virtual camera velocity suitable forrendering and/or displaying a map. An electronic or computing device,such as a mobile phone, personal digital assistant (PDA), laptopcomputer, tablet computer, or portable multifunction device, may in someembodiments selectively obtain map image data according to virtualcamera velocity. Embodiments may implement a display techniquewell-known to those of ordinary skill in the art, a virtual camera. Avirtual camera simulates in virtual space a camera observing image data,just as a physical camera would capture image data. Embodiments maydetermine a level-of-detail for the map image data to render accordingto the map image data observed by a virtual camera. A virtual camera mayobserve both two-dimensional and three-dimensional maps and may operatein two or three dimensions. As a physical camera may change position, sotoo a virtual camera may move between locations in virtual space. Invarious embodiments, a device may detect the velocity of the virtualcamera as it moves between locations. In obtaining the observed mapimage data, a device may do so according to the velocity of the virtualcamera. Once obtained, a device may then render and/or display theobtained map image data.

Detecting the velocity of a virtual camera may be determined throughvarious techniques and devices. Velocity commonly defined is thedistance an object travels divided according to the length of traveltime. Embodiments may implement many forms of input to manipulate avirtual camera, which in turn manipulates the virtual camera's velocity.Some embodiments may allow touch input on a touch sensitive input deviceto manipulate the virtual camera. For example, a leftward swipe gesturemay direct the virtual camera to shift to the right. Some embodimentsmay allow orientation sensors on a device to detect changes in thedevice orientation or movement to manipulate a virtual camera. Locationdata, usually but not limited to data obtained from a location componentor location services, such as Assisted Global Positioning Satellites(A-GPS), may also manipulate the virtual camera. In some embodimentsvirtual camera velocity may include detecting the rotation of a virtualcamera on or about a fixed point.

In order to obtain observed map image, some embodiments may determinewhether the detected virtual camera velocity exceeds a velocitythreshold. There may be one or more velocity thresholds, which may bedetermined according to various factors, such as map image data type,for example raster graphics data or vector graphics data, virtual cameramanipulation input type, such as touch, orientation sensor, or locationcomponent, or the map image data location within the larger virtualspace relative to the virtual camera location. For example, in athree-dimensional map image with a map view looking out to the horizon,the map image data representing the horizon may have a very highvelocity threshold, because little map image data viewable to anobserver changes at a low or high velocity.

Embodiments may then specify a level-of-detail for the map image dataaccording in response to the determination that the detected velocity ofthe virtual camera exceeds the velocity threshold. This specificationmay be implemented by selecting a level-of-detail of the map image datacorresponding to the data's relative distance from the virtual camera invirtual space. For example, image data close to the virtual camera maybe specified with a low level-of-detail, while image data further awayis specified at a high level-of-detail. A device may obtain thedetermined map image data corresponding to this specifiedlevel-of-detail. In some embodiments, a device may obtain the map imagedata from a server, such as a map service. A device may, in someembodiments, access stored map image data, such as memory located on animplementing device. Some embodiments may determine whether all of thedetermined map image data for the map view of the map according to thevelocity of the virtual camera is obtained. In response to determiningthat all of the determined map image data for the map view of the mapaccording to the velocity of the virtual camera is obtained, embodimentsmay determine the map image data of the map without reference to thevirtual camera velocity and obtain the newly determined map image data.

Embodiments of selectively obtaining map image data according to virtualcamera velocity may be implemented in any application that supportsrendering and/or displaying map image data. Example categories ofapplications in which embodiments may be implemented in are mapdisplays, such as in navigation devices, electronic games, which mayinclude rendering or displaying in-game maps, and graphical design,which may allow users to create two-dimensional and three-dimensionalmaps. More generally, embodiments may be implemented in applicationsthat allow map image data to be rendered and/or displayed. Specificexamples of applications or technologies in which embodiments may beimplemented include, but are not limited to, mapping or navigationsoftware applications on an iPod Touch®, iPhone®, or iPad® devices fromApple Inc. of Cupertino, Calif.

Embodiments of selectively obtaining map image data according to virtualcamera velocity may be implemented and performed by a module or modulesimplemented by program instructions stored in a non-transitorycomputer-readable storage medium and executable by one or moreprocessors, such as one or more CPUs or GPUs. An example module that mayimplement some embodiments, and an example application that mayimplement the module, as described herein, is illustrated in FIG. 8. Anexample electronic device on which embodiments may be implemented isillustrated in FIGS. 8 through 11. An example system on whichembodiments may be implemented is illustrated in FIG. 12.

Map Service Operating Environment

Various embodiments may operate within a map service operatingenvironment. FIG. 1 illustrates a map service operating environment,according to some embodiments. A map service 130 may provide mapservices for one or more client devices 102 a-102 c in communicationwith the map service 130 through various communication methods andprotocols. A map service 130 generally may provide map information andother map-related data, such as two-dimensional map image data (e.g.,aerial view of roads utilizing satellite imagery), three-dimensional mapimage data (e.g., traversable map with three-dimensional features, suchas buildings), route and direction calculation (e.g., ferry routecalculations or directions between two points for a pedestrian),real-time navigation data (e.g., turn-by-turn visual navigation data intwo or three dimensions), location data (e.g., where is the clientdevice currently located), and other geographic data (e.g., wirelessnetwork coverage, weather, traffic information, or nearbypoints-of-interest). In various embodiments, the map service data mayinclude localized labels for different countries or regions; localizedlabels may be utilized to present map labels (e.g., street names, citynames, points of interest) in different languages on client devices.Client devices 102 a-102 c may utilize these map services by obtainingmap service data. Client devices 102 a-102 c may implement varioustechniques to process map service data. Client devices 102 a-102 c maythen provide map services to various entities, including, but notlimited to, users, internal software or hardware modules, and/or othersystems or devices external to the client devices 102 a-102 c.

In some embodiments, a map service may be implemented by one or morenodes in a distributed computing system. Each node may be assigned oneor more services or components of a map service. Some nodes may beassigned the same map service or component of a map service. A loadbalancing node may distribute access or requests to other nodes within amap service. In some embodiments a map service may be implemented as asingle system, such as a single server. Different modules or hardwaredevices within a server may implement one or more of the variousservices provided by a map service.

A map service may provide map services by generating map service data invarious formats. In some embodiments, one format of map service data maybe map image data. Map image data may provide image data to a clientdevice so that the client device may process the image data (e.g.,rendering and/or displaying the image data as a two-dimensional orthree-dimensional map). Map image data, whether in two or threedimensions, may specify one or more map tiles. A map tile may be aportion of a larger map image. Assembling together the map tiles of amap may produce the original map. Tiles may be generated from map imagedata, routing or navigation data, or any other map service data. In someembodiments map tiles may be raster-based map tiles, with tile sizesranging from any size both larger and smaller than a commonly-used 256pixel by 256 pixel tile. Raster-based map tiles may be encoded in anynumber of standard digital image representations including, but notlimited to, Bitmap (.bmp), Graphics Interchange Format (.gif), JointPhotographic Experts Group (.jpg, .jpeg, etc.), Portable NetworksGraphic (.png), or Tagged Image File Format (.tiff). In someembodiments, map tiles may be vector-based map tiles, encoded usingvector graphics, including, but not limited to, Scalable Vector Graphics(.svg) or a Drawing File (.drw). Embodiments may also include tiles witha combination of vector and raster data. Metadata or other informationpertaining to the map tile may also be included within or along with amap tile, providing further map service data to a client device. Invarious embodiments, a map tile may be encoded for transport utilizingvarious standards and/or protocols, some of which are described inexamples below.

In various embodiments, map tiles may be constructed from image data ofdifferent resolutions depending on zoom level. For instance, for lowzoom level (e.g., world or globe view), the resolution of map or imagedata need not be as high relative to the resolution at a high zoom level(e.g., city or street level). For example, when in a globe view, theremay be no need to render street level artifacts as such objects would beso small as to be negligible in many cases.

A map service may perform various techniques to analyze a map tilebefore encoding the tile for transport. This analysis may optimize mapservice performance for both client devices and a map service. In someembodiments map tiles may be analyzed for complexity, according tovector-based graphic techniques, and constructed utilizing complex andnon-complex layers. Map tiles may also be analyzed for common image dataor patterns that may be rendered as image textures and constructed byrelying on image masks. In some embodiments, raster-based image data ina map tile may contain certain mask values, which are associate with oneor more textures. Embodiments may also analyze map tiles for specifiedfeatures that may be associated with certain map styles that containstyle identifiers.

Other map services may generate map service data relying upon variousdata formats separate from a map tile. For example, map services thatprovide location data may utilize data formats conforming to locationservice protocols, such as, but not limited to, Radio Resource Locationservices Protocol (RRLP), TIA 801 for Code Division Multiple Access(CDMA), Radio Resource Control (RRC) position protocol, or LTEPositioning Protocol (LPP). Embodiments may also receive or request datafrom client devices identifying device capabilities or attributes (e.g.,hardware specifications or operating system version) or communicationcapabilities (e.g., device communication bandwidth as determined bywireless signal strength or wire or wireless network type).

A map service may obtain map service data from internal or externalsources. For example, satellite imagery used in map image data may beobtained from external services, or internal systems, storage devices,or nodes. Other examples may include, but are not limited to, GPSassistance servers, wireless network coverage databases, business orpersonal directories, weather data, government information (e.g.,construction updates or road name changes), or traffic reports. Someembodiments of a map service may update map service data (e.g., wirelessnetwork coverage) for analyzing future requests from client devices.

Various embodiments of a map service may respond to client devicerequests for map services. These requests may be a request for aspecific map or portion of a map. Embodiments may format requests for amap as requests for certain map tiles. In some embodiments, requests mayalso supply the map service with starting locations (or currentlocations) and destination locations for a route calculation. A clientdevice may also request map service rendering information, such as maptextures or stylesheets. In at least some embodiments, requests may alsobe one of a series of requests implementing turn-by-turn navigation.Requests for other geographic data may include, but are not limited to,current location, wireless network coverage, weather, trafficinformation, or nearby points-of-interest.

A map service may, in some embodiments, may analyze client devicerequests to optimize a device or map service operation. For example, amap service may recognize that the location of a client device is in anarea of poor communications (e.g., weak wireless signal) and send moremap service data to supply a client device in the event of loss incommunication or send instructions to utilize different client hardware(e.g., orientation sensors) or software (e.g., utilize wireless locationservices or Wi-Fi positioning instead of GPS-based services). In anotherexample, a map service may analyze a client device request forvector-based map image data and determine that raster-based map databetter optimizes the map image data according to the image's complexity.Embodiments of other map services may perform similar analysis on clientdevice requests and as such the above examples are not intended to belimiting.

Various embodiments of client devices (e.g., client devices 102 a-102 c)may be implemented on different device types. Examples of aportable-multifunction device include the devices illustrated in FIGS. 8through 11, such as multifunction device 1200 and multifunction device1400. Client devices 102 a-102 c may utilize map service 130 throughvarious communication methods and protocols described below. In someembodiments, client devices 102 a-102 c may obtain map service data frommap service 130. Client devices 102 a-102 c may request or receive mapservice data. Client devices 102 a-102 c may then process map servicedata (e.g., render and/or display the data) and may send the data toanother software or hardware module on the device or to an externaldevice or system.

A client device may, according to some embodiments, implement techniquesto render and/or display maps. These maps may be requested or receivedin various formats, such as map tiles described above. A client devicemay render a map in two-dimensional or three-dimensional views. Someembodiments of a client device may display a rendered map and allow auser, system, or device providing input to manipulate a virtual camerain the map, changing the map display according to the virtual camera'sposition, orientation, and field-of-view. Various forms and inputdevices may be implemented to manipulate a virtual camera. In someembodiments, touch input, through certain single or combination gestures(e.g., touch-and-hold or a swipe) may manipulate the virtual camera.Other embodiments may allow manipulation of the device's physicallocation to manipulate a virtual camera. For example, a client devicemay be tilted up from its current position to manipulate the virtualcamera to rotate up. In another example, a client device may be tiltedforward from its current position to move the virtual camera forward.Other input devices to the client device may be implemented including,but not limited to, auditory input (e.g., spoken words), a physicalkeyboard, mouse, and/or a joystick.

Embodiments may provide various visual feedback to virtual cameramanipulations, such as displaying an animation of possible virtualcamera manipulations when transitioning from two-dimensional map viewsto three-dimensional map views. Embodiments may also allow input toselect a map feature or object (e.g., a building) and highlight theobject, producing a blur effect that maintains the virtual camera'sperception of three-dimensional space.

In some embodiments, a client device may implement a navigation system(e.g., turn-by-turn navigation). A navigation system provides directionsor route information, which may be displayed to a user. Embodiments of aclient device may request directions or a route calculation from a mapservice. A client device may receive map image data and route data froma map service. In some embodiments, a client device may implement aturn-by-turn navigation system, which provides real-time route anddirection information based upon location information and routeinformation received from a map service and/or other location system,such as Global Positioning Satellite (GPS). A client device may displaymap image data that reflects the current location of the client deviceand update the map image data in real-time. A navigation system mayprovide auditory or visual directions to follow a certain route.

A virtual camera may be implemented to manipulate navigation map dataaccording to some embodiments. Some embodiments of client devices mayallow the device to adjust the virtual camera display orientation tobias toward the route destination. Embodiments may also allow virtualcamera to navigation turns simulating the inertial motion of the virtualcamera.

Client devices may implement various techniques to utilize map servicedata from map service. Embodiments may implement some techniques tooptimize rendering of two-dimensional and three-dimensional map imagedata. In some embodiments, a client device may locally store renderinginformation. For example, a client may store a stylesheet which providesrendering directions for image data containing style identifiers. Inanother example, common image textures may be stored to decrease theamount of map image data transferred from a map service. Client devicesmay also implement various modeling techniques to render two-dimensionaland three-dimensional map image data, examples of which include, but arenot limited to: generating three-dimensional buildings out oftwo-dimensional building footprint data; modeling two-dimensional andthree-dimensional map objects to determine the client devicecommunication environment; generating models to determine whether maplabels are seen from a certain virtual camera position; and generatingmodels to smooth transitions between map image data. Some embodiments ofclient devices may also order or prioritize map service data in certaintechniques. For example, a client device may detect the motion orvelocity of a virtual camera, which if exceeding certain thresholdvalues, lower-detail image data will be loaded and rendered of certainareas. Other examples include: rendering vector-based curves as a seriesof points, preloading map image data for areas of poor communicationwith a map service, adapting textures based on display zoom level, orrendering map image data according to complexity.

In some embodiments, client devices may communicate utilizing variousdata formats separate from a map tile. For example, some client devicesmay implement Assisted Global Positioning Satellites (A-GPS) andcommunicate with location services that utilize data formats conformingto location service protocols, such as, but not limited to, RadioResource Location services Protocol (RRLP), TIA 801 for Code DivisionMultiple Access (CDMA), Radio Resource Control (RRC) position protocol,or LTE Positioning Protocol (LPP). Client devices may also receive GPSsignals directly. Embodiments may also send data, with or withoutsolicitation from a map service, identifying the client device'scapabilities or attributes (e.g., hardware specifications or operatingsystem version) or communication capabilities (e.g., devicecommunication bandwidth as determined by wireless signal strength orwire or wireless network type).

FIG. 1 illustrates one possible embodiment of an operating environment100 for a map service 130 and client devices 102 a-102 c. In someembodiments, devices 102 a, 102 b, and 102 c can communicate over one ormore wire or wireless networks 110. For example, wireless network 110,such as a cellular network, can communicate with a wide area network(WAN) 120, such as the Internet, by use of gateway 114. A gateway 114may provide a packet oriented mobile data service, such as GeneralPacket Radio Service (GPRS), or other mobile data service allowingwireless networks to transmit data to other networks, such as wide areanetwork 120. Likewise, access device 112 (e.g., IEEE 802.11g wirelessaccess device) can provide communication access to WAN 120. Devices 102a and 102 b can be any portable electronic or computing device capableof communicating with a map service, such as a portable multifunctiondevice described below with respect to FIGS. 8 to 11. Device 102 c canbe any non-portable electronic or computing device capable ofcommunicating with a map service, such as a system described below inFIG. 12.

In some embodiments, both voice and data communications can beestablished over wireless network 110 and access device 112. Forexample, device 102 a can place and receive phone calls (e.g., usingvoice over Internet Protocol (VoIP) protocols), send and receive e-mailmessages (e.g., using Simple Mail Transfer Protocol (SMTP) or PostOffice Protocol 3 (POP3)), and retrieve electronic documents and/orstreams, such as web pages, photographs, and videos, over wirelessnetwork 110, gateway 114, and WAN 120 (e.g., using Transmission ControlProtocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)).Likewise, in some implementations, devices 102 b and 102 c can place andreceive phone calls, send and receive e-mail messages, and retrieveelectronic documents over access device 112 and WAN 120. In variousembodiments, any of the illustrated client device may communicate withmap service 130 and/or other service(s) 150 using a persistentconnection established in accordance with one or more securityprotocols, such as the Secure Sockets Layer (SSL) protocol or theTransport Layer Security (TLS) protocol.

Devices 102 a and 102 b can also establish communications by othermeans. For example, wireless device 102 a can communicate with otherwireless devices (e.g., other devices 102 a or 102 b, cell phones) overthe wireless network 110. Likewise devices 102 a and 102 b can establishpeer-to-peer communications 140 (e.g., a personal area network) by useof one or more communication subsystems, such as Bluetooth®communication from Bluetooth Special Interest Group, Inc. of Kirkland,Wash. 102 c can also establish peer to peer communications with devices102 a or 102 b. (not pictured). Other communication protocols andtopologies can also be implemented. Devices 102 a and 102 b may alsoreceive Global Positioning Satellite (GPS) signals from GPS 140.

Devices 102 a, 102 b, and 102 c can communicate with map service 130over the one or more wire and/or wireless networks, 110 or 112. Forexample, map service 130 can provide a map service data to renderingdevices 102 a, 102 b, and 102 c. Map service 130 may also communicatewith other services 150 to obtain data to implement map services. Mapservice 130 and other services 150 may also receive GPS signals from GPS140.

In various embodiments, map service 130 and/or other service(s) 150 maybe configured to process search requests from any of client devices.Search requests may include but are not limited to queries for business,address, residential locations, points of interest, or some combinationthereof. Map service 130 and/or other service(s) 150 may be configuredto return results related to a variety of parameters including but notlimited to a location entered into an address bar or other text entryfield (including abbreviations and/or other shorthand notation), acurrent map view (e.g., user may be viewing one location on themultifunction device while residing in another location), currentlocation of the user (e.g., in cases where the current map view did notinclude search results), and the current route (if any). In variousembodiments, these parameters may affect the composition of the searchresults (and/or the ordering of the search results) based on differentpriority weightings. In various embodiments, the search results that arereturned may be a subset of results selected based on specific criteriainclude but not limited to a quantity of times the search result (e.g.,a particular point of interest) has been requested, a measure of qualityassociated with the search result (e.g., highest user or editorialreview rating), and/or the volume of reviews for the search results(e.g., the number of times the search result has been review or rated).

In various embodiments, map service 130 and/or other service(s) 150 maybe configured to provide auto-complete search results that may bedisplayed on the client device, such as within the mapping application.For instance, auto-complete search results may populate a portion of thescreen as the user enters one or more search keywords on themultifunction device. In some cases, this feature may save the user timeas the desired search result may be displayed before the user enters thefull search query. In various embodiments, the auto complete searchresults may be search results found by the client on the client device(e.g., bookmarks or contacts), search results found elsewhere (e.g.,from the internet) by map service 130 and/or other service(s) 150,and/or some combination thereof. As is the case with commands, any ofthe search queries may be entered by the user via voice or throughtyping. The multifunction device may be configured to display searchresults graphically within any of the map display described herein. Forinstance, a pin or other graphical indicator may specify locations ofsearch results as points of interest. In various embodiments, responsiveto a user selection of one of these points of interest (e.g., a touchselection, such as a tap), the multifunction device may be configured todisplay additional information about the selected point of interestincluding but not limited to ratings, reviews or review snippets, hoursof operation, store status (e.g., open for business, permanently closed,etc.), and/or images of a storefront for the point of interest. Invarious embodiments, any of this information may be displayed on agraphical information card that is displayed in response to the user'sselection of the point of interest.

In various embodiments, map service 130 and/or other service(s) 150 mayprovide one or more feedback mechanisms to receive feedback from clientdevices 102 a-c. For instance, client devices may provide feedback onsearch results to map service 130 and/or other service(s) 150 (e.g.,feedback specifying ratings, reviews, temporary or permanent businessclosures, errors etc.); this feedback may be used to update informationabout points of interest in order to provide more accurate or moreup-to-date search results in the future. In some embodiments, mapservice 130 and/or other service(s) 150 may provide testing informationto the client device (e.g., an A/B test) to determine which searchresults are best. For instance, at random intervals, the client devicemay receive and present two search results to a user and allow the userto indicate the best result. The client device may report the testresults to map service 130 and/or other service(s) 150 to improve futuresearch results based on the chosen testing technique, such as an A/Btest technique in which a baseline control sample is compared to avariety of single-variable test samples in order to improve results.

Workflow of Selectively Obtaining Map Image Data

A map display device, such as an electronic navigation system orportable multi-function device, such as described below with respect toFIGS. 8 through 11, may implement a map application, map component, ornavigation component configured to display a map. To display a mapvarious embodiments of the map application, map component, or navigationcomponent may display a map view using a virtual camera. A virtualcamera may determine for a map application, map component, or navigationcomponent the map image data to render for a given map view. Variousembodiments allow the virtual camera to be manipulated, or moved, fromone location to another, creating virtual camera velocity. FIG. 2illustrates a high-level flowchart of a method of selectively obtainingmap image data according to virtual camera velocity, in someembodiments.

Maps are commonly geographic representations of information displayed toan observer. Map image data, therefore, is a digital representation of amap utilizing digital graphics. Map image data may be composed orencoded using many different image formats, including, but not limitedto, raster image formats, such as Bitmap (.bmp), Graphics InterchangeFormat (.gif), Joint Photographic Experts Group (.jpg, .jpeg, etc.),Portable Networks Graphic (.png), or Tagged Image File Format (.tiff),and/or vector image formats, such as Scalable Vector Graphics (.svg) orDrawing File (.drw). Map image data may be a combination of diversegraphics formats. Moreover, portions of map image data, commonly knownas map tiles and discussed above with regard to FIG. 1, may also beutilized to implement map image data.

To render and display map image data, or more generally image data, atechnique well-known to those of ordinary skill in the art uses avirtual camera. As discussed above, a virtual camera operates much likea physical camera. A virtual camera has a location or position withinvirtual space. From this position, a virtual camera may be oriented in adirection in order to observe image data. A virtual camera observesimage data within a field-of-view, usually, but not limited to, arectangular area. Like a physical camera, a virtual camera may changeits position, adjust its orientation, or, in some embodiments, resizeits field-of-view. The virtual space in which a virtual camera operatesis a three-dimensional space. Two-dimensional or three-dimensionalobjects may be observed by a virtual camera in a virtual space. Forexample, FIG. 3A illustrates a virtual camera in virtual space as itobserves two-dimensional map image data. Virtual camera 300 may changeposition in the virtual space 310 to observe the two-dimensional mapimage data 320. Likewise, FIG. 3B illustrates a virtual camera 300 invirtual space 310 as it observes three-dimensional map image data 330.Virtual camera 300 may again change position to observe thethree-dimensional map image data 330 from another angle.

To selectively obtain map image data according to virtual cameravelocity, embodiments may detect the velocity of the virtual camera 210.In some embodiments map image data may be displayed as a series ofimages to create the effect of a moving animation. As a virtual cameratraverses a map, the virtual camera may observe map image data atvarious location points, so that a device may render and display the mapimage data determined at the various location points. At each of theselocation points, the virtual camera's velocity may be detected. Someembodiments may implement various methods, techniques or devices formanipulating the virtual camera to create virtual camera velocity, suchas those described below with respect to FIGS. 4 through 5 c. Forexample, some embodiments may allow touch input, such as gestures obtainvia a touch-sensitive display 1012 in FIG. 10, to direct the movement ofa virtual camera. Determining the velocity in such an embodiment may beimplemented by analyzing the input data received. Embodiments may alsoimplement other input devices, including, but not limited to,orientation sensors or joysticks, to manipulate the virtual camera.Embodiments may also implement techniques such as using a locationcomponent or location services or data to manipulate the virtual camera,such as described below with regard to FIG. 6 c.

Embodiments may then determine a level-of-detail for the map image datafor the map view of a map indicating a level-of-detail for the map imagedata where the level-of-detail is determined according to the velocityof the virtual camera 220. Some embodiments may indicate alevel-of-detail according to numerous variables, including, but notlimited to, map zoom level, map type, object/features in the map imagedata. These variables may then be linked to certain virtual cameravelocities, or ranges of velocities of the virtual camera which arelinked in turn to certain levels-of-detail, or ranges oflevels-of-detail. To determine map image data indicating alevel-of-detail, some embodiments may determine whether the detectedvelocity exceeds a velocity threshold. A velocity threshold is avelocity value or range of values to which embodiments may compare thedetected velocity of a virtual camera. A discussed previously, there maybe one or more velocity thresholds, which may be determined according tovarious factors, such as map image data type, for example rastergraphics data or vector graphics data, virtual camera manipulation inputtype, such as touch, orientation sensor, or location component, or themap image data location within the larger virtual space relative to thevirtual camera location. In response to determining that the detectedvelocity exceeds a velocity threshold, embodiments may specify alevel-of-detail for the map image data. In some embodiments, thespecified level of detail may be determined according to the distancefrom the virtual camera to the location of the map image data in virtualspace. Other varying methods of specifying a level-of-detail for mapimage data including the above example, are discussed below with regardto FIGS. 6 a and 6 b. A specification for level of detail may berecorded or identified in a temporary or permanent data structure thatassembles map image data information about the current map image data.

Embodiments may then obtain the determined map image data 230.Determined map image data may indicate a default level-of-detail. Forexample, a virtual camera may have a detected velocity of 5 which isthen compared to a velocity threshold of 20. Because the velocity doesnot exceed the velocity threshold, a device may obtain the map imagedata from a map service and/or access map image data stored locally,retrieving the default level-of-detail indicated for the map image data.FIG. 7 provides a visual example of this possibility at elements 803 and804. Obtaining map image data may occur by obtaining the map image datafrom a map service, such as map service 130 described above in FIG. 1,or any other server sending map image data to a client device. Obtainingmap image data may also occur by accessing map image data storedlocally, such as in memory 1002 in FIG. 8.

After obtaining the determined map image data, some embodiments may thenrender the observed map image data. Many rendering devices andtechniques are well-known to those of ordinary skill in the art. Theobtained map image data may be encoded utilizing the various image dataformats, discussed above. Map image data may be a combination of dataformats and types, such as raster image data, vector image data, or acombination of both. Common techniques to render various types of mapimage data such as, but not limited to, may include utilizing the OpenGraphics Library (OpenGL) or Direct3D application programmer interfaces,or variants thereof such as OpenGL ES. Customized rendering applicationswhich may optimize the performance of CPUs or GPUs may also beimplemented. Rendering raster data may be implemented by decoding ordecompressing, raster data according to its format and, if displayingthe raster data, submitting the raster data to a hardware device, suchas a frame buffer, which displays the raster data. Vector image data maybe rendered implementing many well-known rendering pipelines thattransform the vector primitives into a raster image, which may besubmitted to a hardware device, such as a frame buffer. Other softwarestructures and devices may be used store pre-rendered and rendered data,combining one or more types of image data in a single image. Many othersoftware and hardware implementations may be used to render the observedmap image data. In some embodiments the rendered map image data may bedisplayed on the rendering device. Embodiments may also store therendered map image data or send the map image data to other modules orapplications for further processing.

FIGS. 4 a and 4 b illustrate an example display of map data selectivelyobtained according to virtual camera velocity. Portable multi-functiondevice 400, as described below with respect to FIGS. 9 through 12,displays a map view of the same map area in FIG. 4 a and FIG. 4 b. InFIG. 4 a, the virtual camera velocity has exceed the given threshold, solower level detail is obtained. River feature 404 and park feature 402have simple shading patterns to fill their space. In FIG. 4 b, thevirtual camera is at zero velocity, or still, so full detail map data isobtained. Park feature 406 has trees and shrubs in the displayed textureand river feature 408 has a wave texture. Many different examples of lowand high level detail, as well as areas where such detail may bedisplayed may be implemented. The above figures are not intended to belimiting.

Various embodiments may determine whether all of the determined mapimage data for the map view of the map according to the velocity of thevirtual camera is obtained. For example, a map application may implementa download tracker. This download tracker identifies what map image datais sought, from what source the map image data is sought, the indicatedlevel-of-detail for the map image data, and whether it has beenreceived. Such a download tracker may determine whether all of thedetermined map image data is obtained by examining whether the map imagedata has been received. In response to determining that all of thedetermined map image data is obtained, embodiments may determine the mapimage data for the map view and obtain the determined map image data.Continuing the above example, the download tracker may instruct anothercomponent within a map application to obtain, without reference to alevel-of-detail, the sought map image data. The above example is one ofmany possible implementations of determining whether the determined mapimage data is obtained, and is not intended to be limiting. Many otherhardware implementations, such as through download or display buffers,software implementations, such as through various data structures,and/or combination of thereof may be envisioned.

Detecting Virtual Camera Velocity

To determine map image data indicating a level-of-detail where thelevel-of-detail is determined according to the velocity of the virtualcamera, as indicated at 220 in FIG. 2, the virtual camera velocity mustbe determined, as indicated at 210. Detecting a virtual camera'svelocity, in some embodiments may involve analyzing the movement betweenpositions in virtual space and/or the input of various devices. In manyembodiments, detecting the velocity of the may be implemented byanalyzing the movement of the virtual camera itself without regard tothe instigation of the movement of the virtual camera. As velocity isgenerally considered to be the distance between two points, divided bythe amount of time taken to travel between the two points, a simplecalculation may provide the velocity of the virtual camera. However, insome embodiments velocity may be more broadly construed to encompass therotation of a virtual camera about a fixed position in virtual space.

FIG. 5 illustrates the rotation of a virtual camera about a fixedposition and may illuminate how some embodiments detect virtual cameravelocity. Virtual camera 500 is positioned at fixed point in virtualspace. Virtual camera 500 may begin by orienting its field of view inthe direction 502. The virtual camera 500 may then rotate a certaindistance according to the angle θ₁ till it faces the direction 504. Someembodiments may determine a velocity by calculating the distance betweenthe two directions, 502 and 504, according to the angle θ₁, and the timeto turn between direction 502 and 504. Note the distance between the twodirections expands according to the degree of the angle, θ₁. Therefore,in some embodiments determining the velocity of a virtual camerarotating on or about a fixed point, multiple velocity determinations maybe detected for different portions of the map image data according totheir relative distance from the virtual camera.

In at least some embodiments, a virtual camera may be manipulatedaccording to input from a touch-sensitive input device, such astouch-sensitive display 1012 in FIG. 11. FIG. 6 a illustrates an exampleof touch input to a touch-sensitive input device and its effect upon themovement of a virtual camera. Virtual camera 602 is observing map imagedata 606 on a portable multifunction device 608. A user may providetouch input 604, which is illustrated as a swipe gesture to the right ofthe device. In turn, the virtual camera 602 may move in direction 610,observing new map image data along the way. A device may analyze theswipe gesture, for example the length of it and the time from beginningto end of it, to determine the velocity of the virtual camera 602 inmanipulation direction 610. Some embodiments may measure the effect ofthe input on the virtual camera, essentially measuring the distancebetween the starting point and current point of the virtual camera andthe time the virtual camera took to travel between the two points.

In at least some embodiments, a virtual camera may be manipulatedaccording to input from orientation sensors, such as orientation sensors1068 described with regard to FIG. 9. FIG. 6 b illustrates an example oforientation sensor input and its effect upon the movement of a virtualcamera. Virtual camera 628 observes map image data 626 on portablemultifunction device 620. Orientation sensors may detect a change in adevice's orientation, such as a direction tilting forward 622 or tiltingside-to-side 624. A user may tilt the portable multifunction device 620forward 622, and in turn the virtual camera 628 may move along thecorresponding direction 622, observing new map image data along the way.Likewise a user may tilt the portable multifunction device 620 to oneside 624 and the virtual camera 628 may move along the correspondingdirection 622, observing new map image data along the way. A device mayanalyze the tilting motion, for example by determining the angle betweento positions and the time from beginning to end of the motion, todetermine the velocity of virtual camera 628.

In at least some embodiments, a virtual camera may be manipulatedaccording to location data obtained from a location component orlocation service. FIG. 6 c illustrates an example of location data andits effect upon the movement of a virtual camera. Location data may beobtained by a device that is changing geographic location. A device, forexample, may be moved by a pedestrian, a motor vehicle, a bicycle, oranother method of movement or transportation. Location point A 642represents a portable multifunction device 660 moving in an automobileat point A. Location point B 644 represents the same device 660 movingin an automobile at point B. At both points, a device may communicatewith a location service 670, relying on such technologies, including butnot limited to, GPS, A-GPS, location by Internet Protocol (IP)connections, or WiFi connection locations, to retrieve a physicallocation of the device at each point 642 and 644. These changes inlocation may be utilized by a virtual camera 660 observing map imagedata 650 on portable multifunction device 660. The device 660 may locatethe virtual camera's 640 position in virtual space relative to thedetected locations in physical space. The device 660 may move thevirtual camera from location point A 642 to location point B 644relative to the distance and direction moved between location point A642 and location point B 644. A device may analyze the distance and timetraveled between the two location points in virtual space to determinethe velocity of virtual camera 640.

The previous examples and illustrations are examples of many possibleimplementations of detecting virtual camera velocity and are notintended to be limiting. Any manipulation or movement in a virtualspace, whether by internal or external input, may be able to determinethe virtual camera's velocity according to well-known velocityequations. Persons having ordinary skill in the art will recognize themany different configurations of hardware and software capable of makinga velocity determination for a virtual camera.

Indicating Map Image Data Level-of-Detail

In various embodiments a device may detect a virtual camera's velocity,such as through the techniques discussed above with regard to FIGS. 5through 6 c. Various embodiments may determine map image data for themap view of the map indicating level-of-detail for the map image detailaccording to the velocity of the virtual camera, as indicated at 220 inFIG. 2. Some embodiments may indicate a level-of-detail according tonumerous variables, including, but not limited to, map zoom level, maptype, object/features in the map image data. These variables may then belinked to certain virtual camera velocities, or ranges of velocities ofthe virtual camera which are linked in turn to certain levels-of-detail,or ranges of levels-of-detail. For example, when the velocity of avirtual camera is detected, a device may access a level-of-detail indexfor the given map at a certain zoom level which indicates a particularlevel-of-detail according to the detected zoom level. Some embodimentsmay determine whether the detected velocity exceeds a velocitythreshold. In response to such a determination of velocity that exceedsa velocity threshold, embodiments may specify a level-of-detail for themap image data. Various levels-of-detail may be specified for map imagedata, and multiple levels-of-detail may be obtained, processed,transmitted, rendered, or displayed. A level-of-detail may be the mapimage data size, resolution, complexity, or other factor that increasesthe rendering time of the map image data. For example, map image datacontaining a coast line, may at high levels-of-detail be described usingraster graphics data. However, at a certain level-of-detail and below,the lake may be described more simply using vector graphics data. Thereare many different techniques of implementing multiple level-of-detailsfor map image data well-known to those of ordinary skill in the art.Another example, such as mipmaps, may provide various levels-of-detailfor map image data in various embodiments.

Embodiments may implement rendering map image data with high and lowlevel-of-detail. The terms high and low do not necessarily indicate orspecify a single level-of-detail, such as a single resolution, but mayconnote a range of lower level-of-detail or higher level-of-detail asimplemented in a particular set of map image data. For example, a mapcomposed of map image data may have eight levels of resolution. Thefirst five levels may be considered low level-of-detail, while theremaining three are considered high level-of-detail. A device mayindicate or specify any one of the first five, low level-of-detailsaccording to a virtual cameras velocity. A device may take into accountnumerous factors to make a determination within a range of low or highlevel-of-details, including but not limited to the surrounding imagedata level-of-detail, the current rendering capability of the device, orcommunication capability with a map service, such as described inFIG. 1. Any particular specification within a range for both low andhigh is encompassed in the various embodiments presented, as well asthose implementations where just two specific image datalevels-of-detail are available. High and low level-of-detail may also bedetermined relative to a default or standard level-of-detail for mapimage data. Level-of-detail may be lowered or increased in varyingdegrees, such as by one level at a time or skipping various levels whenraising or lowering.

Some embodiments may select the level-of-detail for the map image dataaccording to a distance from the virtual camera to a location of the mapimage data in a virtual space. For example, FIGS. 7 a and 7 b illustratediffering levels of relative distance in virtual space from a virtualcamera with varying levels-of-detail specified for map image data withinthe distance range. In FIG. 7 a, virtual camera 700, observes map imagedata 710 according to a field of view. Image data relatively close indistance 720 to the virtual camera 700 is specified to a lowlevel-of-detail. Whereas, the image data relatively far in distance 730from the virtual camera 700 is specified with a high level-of-detail.FIG. 7 b represents an opposite scenario. Virtual camera 700, observesmap image data 710 according to a field of view. Image data relativelyclose in distance 720 to the virtual camera 700 is specified to a highlevel-of-detail. Whereas, the image data relatively far in distance 730from the virtual camera 700 is specified with a low level-of-detail.

The above examples are two of many possible implementations ofselectively obtaining map image data according to virtual cameravelocity and are not intended to be limiting. For example both examplesmay be implemented as two of many different scenarios on a device whichmay be selected according to various factors, for example map imagetype. FIG. 7 a, for example, may be suited to map image data that isimplementing a navigation system, such as turn by turn map imagedisplay, such as displayed in FIG. 12. As the data that is closest to aviewer is moving by very quickly, it need not be viewed a highlevel-of-detail. Meanwhile, map image data on the horizon or fardistance, may appear relatively the same, and therefore be rendered at ahigh level-of-detail. FIG. 7 b, in another example, may best be utilizedin the scenario where a viewer of map image data is rotating their viewin a fixed position. The map image data close to the viewer will appearto be moving slower, and subject to higher viewer scrutiny. Thus, mapimage data relatively close to the viewer will be rendered in highlevel-of-detail, while the map image data relatively far from the viewerwill be rendered in low level-of-detail. Other embodiments may bedisplaying an aerial view of a map. For this type of embodiment, anyvirtual camera motion at all may lessen the viewable quality of an imageby a viewer, so the same level-of-detail may be specified for the mapimage data.

Indicating a level-of-detail for obtaining map image data may beimplemented when obtaining the determined map image data, indicated at230 in FIG. 2, by formatting request messages to a map service, such asmap service 130 described with regard to FIG. 1, in some embodiments.These requests may specify a specific level-of-detail, or request a highor low level-of-detail, from which the map service may determine theparticular map image data with the specified level-of-detail toretrieve. Embodiments may also implement certain local data structuresand/or storage buffers or devices to store multiple level-of-details ofmap image data, such as in memory 1002 in FIG. 9. Such data structuresor devices may be located internal or external to any graphics orrendering pipelines or hardware devices, such as GPUs and/or CPUs.Various forms of hardware logic or software implementation may determinea specific map image data level-of-detail within a range of high or lowlevel-of-details.

Example Embodiments

Various embodiments may implement selectively obtaining map image dataaccording to virtual camera velocity. In some embodiments, a map module,application, component or navigation component may be implemented toselectively obtain map image data according to virtual camera velocity.For example, an electronic navigation device may implement a navigationcomponent according to the various methods and techniques described withregard to FIGS. 2 through 7 b. In another example, a portablemulti-function device, such as described below with respect to FIGS. 9through 12, may implement a map application according to the variousmethods and techniques described with regard to FIGS. 2 through 7 b.FIG. 8 illustrates a map module (or component, application, ornavigation component), according to some embodiments. The map module maybe implemented on an electronic or computing device, such as a portablemultifunction device described below with respect to FIGS. 9 through 12,or on a system such as described below with respect to FIG. 13.

The map module 800 may first determine the map image data observed by avirtual camera 801. For example, a device implementing the module may berendering and/or displaying a three-dimensional street map from anaerial perspective, which a virtual camera may observe. Various forms ofinput, external and internal to the map rendering module may manipulatethe position and/or orientation of the virtual camera. A locationservice (or location component) 810, such as one implemented by A-GPS,may provide location data to a map rendering module 800, which in turnmoves the virtual camera observing the map image data in virtual space.Likewise, touch input 820, such as a gesture, tap, or multiple touch,may also move the virtual camera observing the map image data in virtualspace. Orientation sensors 830 may provide additional input to move thevirtual camera observing the map image data in virtual space. The maprendering module 800 may analyze directly the input of location service810, touch input 820, or orientation sensors 830, or analyze the effectof the input on the virtual camera in order to detect the velocity ofthe virtual camera 802.

As indicated at 803, the map rendering module 800 may determine whetherthe detected velocity exceeds a velocity threshold 803. This velocitythreshold may be a single value, or a range of values depending on therelative location of the map image data in virtual space, the positionor movement of the virtual camera (e.g., a rotation versus a change inposition in virtual space), or a particular mode of the deviceimplementing the map rendering module 800 (e.g., navigation mode, mapdisplay mode, directions, etc.).

If the velocity threshold is exceeded, a map rendering module 800 maythen specify the map image data level-of-detail 804. This specificationmay occur according to the determination of whether the detectedvelocity exceeds the velocity threshold. Then (or if the detectedvelocity did not exceed the velocity threshold), a map rendering module800, may request map image data corresponding to the specifiedlevel-of-detail 805 from a map service 840, such as map service 130described in FIG. 1. This request may be formatted relying on variouswell-known messaging structures and schemes using the variouscommunication channels described with regard to FIG. 1 and clientdevices 102. A map service 840, may operate within the context of a mapservice operating environment, such as illustrated in FIG. 1. The mapservice may determine the map image data requested by the map renderingmodule 800 and return the map image data at the specifiedlevel-of-detail. A map rendering module may then load map image datacorresponding to the specified level-of-detail 806 from map storage 850,such as memory 1002 in FIG. 9, which may be situated locally on animplementing device.

After requesting map image data 805 and loading map image data 806, amap rendering module 800 may render the map image data 807. A maprendering module 800 may then submit the rendered map image data to adisplay 860, such as touch-sensitive display 1012 in FIG. 11, to astorage medium 870, such as internal or external memory, and/or to othermodules 880, such as other applications that may further process orappend data to the rendered map information.

Example Electronic Device

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), may also beused. It should also be understood that, in some embodiments, the deviceis not a portable communications device, but is a desktop computer witha touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the device is a gaming computer withorientation sensors (e.g., orientation sensors in a gaming controller).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that are intuitive andtransparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 9 is a block diagram illustratingportable multifunction device 1000 with touch-sensitive displays 1012 inaccordance with some embodiments. Touch-sensitive display 1012 issometimes called a “touch screen” for convenience, and may also be knownas or called a touch-sensitive display system. Device 1000 may includememory 1002 (which may include one or more computer readable storagemediums), memory controller 1022, one or more processing units (CPU's)1020, peripherals interface 1018, RF circuitry 1008, audio circuitry1010, speaker 1011, microphone 1013, input/output (I/O) subsystem 1006,other input or control devices 1016, and external port 1024. Device 1000may include one or more optical sensors 1064. These components maycommunicate over one or more communication buses or signal lines 1003.

It should be appreciated that device 1000 is only one example of aportable multifunction device, and that device 1000 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIG. 9 may be implemented in hardware,software, or a combination of both hardware and software, including oneor more signal processing and/or application specific integratedcircuits.

Memory 1002 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 1002 by other components of device 1000, suchas CPU 1020 and the peripherals interface 1018, may be controlled bymemory controller 1022.

Peripherals interface 1018 can be used to couple input and outputperipherals of the device to CPU 1020 and memory 1002. The one or moreprocessors 1020 run or execute various software programs and/or sets ofinstructions stored in memory 1002 to perform various functions fordevice 1000 and to process data.

In some embodiments, peripherals interface 1018, CPU 1020, and memorycontroller 1022 may be implemented on a single chip, such as chip 1004.In some other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 1008 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 1008 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 1008 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 1008 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of multiple communications standards, protocols and technologies,including but not limited to Global System for Mobile Communications(GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packetaccess (HSDPA), high-speed uplink packet access (HSUPA), wideband codedivision multiple access (W-CDMA), code division multiple access (CDMA),time division multiple access (TDMA), Bluetooth, Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 1010, speaker 1011, and microphone 1013 provide an audiointerface between a user and device 1000. Audio circuitry 1010 receivesaudio data from peripherals interface 1018, converts the audio data toan electrical signal, and transmits the electrical signal to speaker1011. Speaker 1011 converts the electrical signal to human-audible soundwaves. Audio circuitry 1010 also receives electrical signals convertedby microphone 1013 from sound waves. Audio circuitry 1010 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 1018 for processing. Audio data may be retrievedfrom and/or transmitted to memory 1002 and/or RF circuitry 1008 byperipherals interface 1018. In some embodiments, audio circuitry 1010also includes a headset jack (e.g., 1212, FIG. 11). The headset jackprovides an interface between audio circuitry 1010 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 1006 couples input/output peripherals on device 1000, suchas touch screen 1012 and other input control devices 1016, toperipherals interface 1018. I/O subsystem 1006 may include displaycontroller 1056 and one or more input controllers 1060 for other inputor control devices. The one or more input controllers 1060 receive/sendelectrical signals from/to other input or control devices 1016. Theother input control devices 1016 may include physical buttons (e.g.,push buttons, rocker buttons, etc.), dials, slider switches, joysticks,click wheels, and so forth. In some alternate embodiments, inputcontroller(s) 1060 may be coupled to any (or none) of the following: akeyboard, infrared port, USB port, and a pointer device such as a mouse.The one or more buttons (e.g., 1208, FIG. 11) may include an up/downbutton for volume control of speaker 1011 and/or microphone 1013. Theone or more buttons may include a push button (e.g., 1206, FIG. 11).

Touch-sensitive display 1012 provides an input interface and an outputinterface between the device and a user. Display controller 1056receives and/or sends electrical signals from/to touch screen 1012.Touch screen 1012 displays visual output to the user. The visual outputmay include graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output may correspond to user-interface objects.

Touch screen 1012 has a touch-sensitive surface, sensor or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 1012 and display controller 1056 (along with anyassociated modules and/or sets of instructions in memory 1002) detectcontact (and any movement or breaking of the contact) on touch screen1012 and converts the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages orimages) that are displayed on touch screen 1012. In an exemplaryembodiment, a point of contact between touch screen 1012 and the usercorresponds to a finger of the user.

Touch screen 1012 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 1012 and display controller 1056 maydetect contact and any movement or breaking thereof using any ofmultiple touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 1012. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 1012 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 1060 dpi. The user may make contact with touch screen 1012using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 1000 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 1012 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 1000 also includes power system 1062 for powering the variouscomponents. Power system 1062 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 1000 may also include one or more optical sensors 1064. FIG. 9shows an optical sensor coupled to optical sensor controller 1058 in I/Osubsystem 1006. Optical sensor 1064 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 1064 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 1043(also called a camera module), optical sensor 1064 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 1000, opposite touch screen display 1012 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image may be obtained for videoconferencingwhile the user views the other video conference participants on thetouch screen display.

Device 1000 may also include one or more proximity sensors 1066. FIG. 9shows proximity sensor 1066 coupled to peripherals interface 1018.Alternately, proximity sensor 1066 may be coupled to input controller1060 in I/O subsystem 1006. In some embodiments, the proximity sensorturns off and disables touch screen 1012 when the multifunction deviceis placed near the user's ear (e.g., when the user is making a phonecall).

Device 1000 includes one or more orientation sensors 1068. In someembodiments, the one or more orientation sensors include one or moreaccelerometers (e.g., one or more linear accelerometers and/or one ormore rotational accelerometers). In some embodiments, the one or moreorientation sensors include one or more gyroscopes. In some embodiments,the one or more orientation sensors include one or more magnetometers.In some embodiments, the one or more orientation sensors include one ormore of global positioning system (GPS), Global Navigation SatelliteSystem (GLONASS), and/or other global navigation system receivers. TheGPS, GLONASS, and/or other global navigation system receivers may beused for obtaining information concerning the location and orientation(e.g., portrait or landscape) of device 1000. In some embodiments, theone or more orientation sensors include any combination oforientation/rotation sensors. FIG. 9 shows the one or more orientationsensors 1068 coupled to peripherals interface 1018. Alternately, the oneor more orientation sensors 1068 may be coupled to an input controller1060 in I/O subsystem 1006. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreorientation sensors.

In some embodiments, the software components stored in memory 1002include operating system 1026, communication module (or set ofinstructions) 1028, contact/motion module (or set of instructions) 1030,graphics module (or set of instructions) 1032, text input module (or setof instructions) 1034, Global Positioning System (GPS) module (or set ofinstructions) 1035, and applications (or sets of instructions) 1036.Furthermore, in some embodiments memory 1002 stores device/globalinternal state 1057, as shown in FIG. 9. Device/global internal state1057 includes one or more of: active application state, indicating whichapplications, if any, are currently active; display state, indicatingwhat applications, views or other information occupy various regions oftouch screen display 1012; sensor state, including information obtainedfrom the device's various sensors and input control devices 1016; andlocation information concerning the device's location and/or attitude.

Operating system 1026 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS,or an embedded operating system such as VxWorks) includes varioussoftware components and/or drivers for controlling and managing generalsystem tasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 1028 facilitates communication with other devicesover one or more external ports 1024 and also includes various softwarecomponents for handling data received by RF circuitry 1008 and/orexternal port 1024. External port 1024 (e.g., Universal Serial Bus(USB), FIREWIRE, etc.) is adapted for coupling directly to other devicesor indirectly over a network (e.g., the Internet, wireless LAN, etc.).In some embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 1030 may detect contact with touch screen 1012 (inconjunction with display controller 1056) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 1030 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 1030receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 1030 and display controller 1056detect contact on a touchpad.

Contact/motion module 1030 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 1032 includes various known software components forrendering and displaying graphics on touch screen 1012 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 1032 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 1032 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 1056.

Text input module 1034, which may be a component of graphics module1032, provides soft keyboards for entering text in various applications(e.g., contacts 1037, e-mail 1040, IM 1041, browser 1047, and any otherapplication that needs text input).

GPS module 1035 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 1038 foruse in location-based dialing, to camera 1043 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 1036 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 1037 (sometimes called an address book or        contact list);    -   telephone module 1038;    -   video conferencing module 1039;    -   e-mail client module 1040;    -   instant messaging (IM) module 1041;    -   workout support module 1042;    -   camera module 1043 for still and/or video images;    -   image management module 1044;    -   browser module 1047;    -   calendar module 1048;    -   widget modules 1049, which may include one or more of: weather        widget 1049-1, stocks widget 1049-2, calculator widget 1049-3,        alarm clock widget 1049-4, dictionary widget 1049-5, and other        widgets obtained by the user, as well as user-created widgets        1049-6;    -   widget creator module 1050 for making user-created widgets        1049-6;    -   search module 1051;    -   video and music player module 1052, which may be made up of a        video player    -   module and a music player module;    -   notes module 1053;    -   map module 1054; and/or    -   online video module 1055.

Examples of other applications 1036 that may be stored in memory 1002include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 1012, display controller 1056, contactmodule 1030, graphics module 1032, and text input module 1034, contactsmodule 1037 may be used to manage an address book or contact list (e.g.,stored in application internal state 1092 of contacts module 1037 inmemory 1002), including: adding name(s) to the address book; deletingname(s) from the address book; associating telephone number(s), e-mailaddress(es), physical address(es) or other information with a name;associating an image with a name; categorizing and sorting names;providing telephone numbers or e-mail addresses to initiate and/orfacilitate communications by telephone 1038, video conference 1039,e-mail 1040, or IM 1041; and so forth.

In conjunction with RF circuitry 1008, audio circuitry 1010, speaker1011, microphone 1013, touch screen 1012, display controller 1056,contact module 1030, graphics module 1032, and text input module 1034,telephone module 1038 may be used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in address book 1037, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication may use any of multiple communicationsstandards, protocols and technologies.

In conjunction with RF circuitry 1008, audio circuitry 1010, speaker1011, microphone 1013, touch screen 1012, display controller 1056,optical sensor 1064, optical sensor controller 1058, contact module1030, graphics module 1032, text input module 1034, contact list 1037,and telephone module 1038, videoconferencing module 1039 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 1008, touch screen 1012, displaycontroller 1056, contact module 1030, graphics module 1032, and textinput module 1034, e-mail client module 1040 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 1044,e-mail client module 1040 makes it very easy to create and send e-mailswith still or video images taken with camera module 1043.

In conjunction with RF circuitry 1008, touch screen 1012, displaycontroller 1056, contact module 1030, graphics module 1032, and textinput module 1034, the instant messaging module 1041 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 1008, touch screen 1012, displaycontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, GPS module 1035, map module 1054, and music player module1046, workout support module 1042 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store and transmit workoutdata.

In conjunction with touch screen 1012, display controller 1056, opticalsensor(s) 1064, optical sensor controller 1058, contact module 1030,graphics module 1032, and image management module 1044, camera module1043 includes executable instructions to capture still images or video(including a video stream) and store them into memory 1002, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 1002.

In conjunction with touch screen 1012, display controller 1056, contactmodule 1030, graphics module 1032, text input module 1034, and cameramodule 1043, image management module 1044 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, and textinput module 1034, browser module 1047 includes executable instructionsto browse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, e-mail client module 1040, and browser module 1047,calendar module 1048 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, and browser module 1047, widget modules 1049 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 1049-1, stocks widget 1049-2, calculator widget 1049-3,alarm clock widget 1049-4, and dictionary widget 1049-5) or created bythe user (e.g., user-created widget 1049-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, and browser module 1047, the widget creator module 1050 maybe used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 1012, display system controller 1056,contact module 1030, graphics module 1032, and text input module 1034,search module 1051 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 1002 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 1012, display system controller 1056,contact module 1030, graphics module 1032, audio circuitry 1010, speaker1011, RF circuitry 1008, and browser module 1047, video and music playermodule 1052 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 1012 or on an external, connected display via external port1024). In some embodiments, device 1000 may include the functionality ofan MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 1012, display controller 1056, contactmodule 1030, graphics module 1032, and text input module 1034, notesmodule 1053 includes executable instructions to create and manage notes,to do lists, and the like in accordance with user instructions.

In conjunction with RF circuitry 1008, touch screen 1012, display systemcontroller 1056, contact module 1030, graphics module 1032, text inputmodule 1034, GPS module 1035, and browser module 1047, map module 1054may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 1012, display system controller 1056,contact module 1030, graphics module 1032, audio circuitry 1010, speaker1011, RF circuitry 1008, text input module 1034, e-mail client module1040, and browser module 1047, online video module 1055 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 1024), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 1041, rather than e-mail client module 1040, isused to send a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. In some embodiments, memory 1002 maystore a subset of the modules and data structures identified above.Furthermore, memory 1002 may store additional modules and datastructures not described above.

In some embodiments, device 1000 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device1000, the number of physical input control devices (such as pushbuttons, dials, and the like) on device 1000 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 1000 to a main, home, or root menu from any userinterface that may be displayed on device 1000. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 9 is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 1002 (in FIG. 10) includes event sorter 170 (e.g., in operatingsystem 1026) and a respective application 1036-1 (e.g., any of theaforementioned applications 1037-1051, 1055).

Event sorter 1070 receives event information and determines theapplication 1036-1 and application view 1091 of application 1036-1 towhich to deliver the event information. Event sorter 1070 includes eventmonitor 1071 and event dispatcher module 1074. In some embodiments,application 1036-1 includes application internal state 1092, whichindicates the current application view(s) displayed on touch sensitivedisplay 1012 when the application is active or executing. In someembodiments, device/global internal state 1057 is used by event sorter1070 to determine which application(s) is (are) currently active, andapplication internal state 1092 is used by event sorter 1070 todetermine application views 1091 to which to deliver event information.

In some embodiments, application internal state 1092 includes additionalinformation, such as one or more of: resume information to be used whenapplication 1036-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 1036-1, a state queue for enabling the user to go back toa prior state or view of application 1036-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 1071 receives event information from peripherals interface1018. Event information includes information about a sub-event (e.g., auser touch on touch sensitive display 1012, as part of a multi-touchgesture). Peripherals interface 1018 transmits information it receivesfrom I/O subsystem 1006 or a sensor, such as proximity sensor 1066,orientation sensor(s) 1068, and/or microphone 1013 (through audiocircuitry 1010). Information that peripherals interface 1018 receivesfrom I/O subsystem 1006 includes information from touch-sensitivedisplay 1012 or a touch-sensitive surface.

In some embodiments, event monitor 1071 sends requests to theperipherals interface 1018 at predetermined intervals. In response,peripherals interface 1018 transmits event information. In otherembodiments, peripheral interface 1018 transmits event information onlywhen there is a significant event (e.g., receiving an input above apredetermined noise threshold and/or for more than a predeterminedduration).

In some embodiments, event sorter 1070 also includes a hit viewdetermination module 1072 and/or an active event recognizerdetermination module 1073.

Hit view determination module 1072 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 1012 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 1072 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 1072identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 1073 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 1073 determines that only the hit view should receive aparticular sequence of sub-events. In other embodiments, active eventrecognizer determination module 1073 determines that all views thatinclude the physical location of a sub-event are actively involvedviews, and therefore determines that all actively involved views shouldreceive a particular sequence of sub-events. In other embodiments, evenif touch sub-events were entirely confined to the area associated withone particular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 1080). In embodiments includingactive event recognizer determination module 1073, event dispatchermodule 1074 delivers the event information to an event recognizerdetermined by active event recognizer determination module 1073. In someembodiments, event dispatcher module 1074 stores in an event queue theevent information, which is retrieved by a respective event receivermodule 1082.

In some embodiments, operating system 1026 includes event sorter 1070.Alternatively, application 1036-1 includes event sorter 1070. In yetother embodiments, event sorter 1070 is a stand-alone module, or a partof another module stored in memory 1002, such as contact/motion module1030.

In some embodiments, application 1036-1 includes multiple event handlers1090 and one or more application views 1091, each of which includesinstructions for handling touch events that occur within a respectiveview of the application's user interface. Each application view 1091 ofthe application 1036-1 includes one or more event recognizers 1080.Typically, a respective application view 1091 includes multiple eventrecognizers 1080. In other embodiments, one or more of event recognizers1080 are part of a separate module, such as a user interface kit (notshown) or a higher level object from which application 1036-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 1090 includes one or more of: data updater 1076, object updater1077, GUI updater 1078, and/or event data 1079 received from eventsorter 1070. Event handler 1090 may utilize or call data updater 1076,object updater 1077 or GUI updater 1078 to update the applicationinternal state 1092. Alternatively, one or more of the application views1091 includes one or more respective event handlers 1090. Also, in someembodiments, one or more of data updater 1076, object updater 1077, andGUI updater 1078 are included in a respective application view 1091.

A respective event recognizer 1080 receives event information (e.g.,event data 1079) from event sorter 1070, and identifies an event fromthe event information. Event recognizer 1080 includes event receiver1082 and event comparator 1084. In some embodiments, event recognizer1080 also includes at least a subset of: metadata 1083, and eventdelivery instructions 1088 (which may include sub-event deliveryinstructions).

Event receiver 1082 receives event information from event sorter 1070.The event information includes information about a sub-event, forexample, a touch or a touch movement. Depending on the sub-event, theevent information also includes additional information, such as locationof the sub-event. When the sub-event concerns motion of a touch theevent information may also include speed and direction of the sub-event.In some embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 1084 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 1084 includes eventdefinitions 1086. Event definitions 1086 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(1087-1), event 2 (1087-2), and others. In some embodiments, sub-eventsin an event 1087 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (1087-1) is a double tap on a displayed object.The double tap, for example, includes a first touch (touch begin) on thedisplayed object for a predetermined phase, a first lift-off (touch end)for a predetermined phase, a second touch (touch begin) on the displayedobject for a predetermined phase, and a second lift-off (touch end) fora predetermined phase. In another example, the definition for event 2(1087-2) is a dragging on a displayed object. The dragging, for example,includes a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 1012, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 1090.

In some embodiments, event definition 1087 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 1084 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 1012, when a touch is detected ontouch-sensitive display 1012, event comparator 1084 performs a hit testto determine which of the three user-interface objects is associatedwith the touch (sub-event). If each displayed object is associated witha respective event handler 1090, the event comparator uses the result ofthe hit test to determine which event handler 1090 should be activated.For example, event comparator 1084 selects an event handler associatedwith the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 1087 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 1080 determines that the series ofsub-events do not match any of the events in event definitions 1086, therespective event recognizer 1080 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 1080 includesmetadata 1083 with configurable properties, flags, and/or lists thatindicate how the event delivery system should perform sub-event deliveryto actively involved event recognizers. In some embodiments, metadata1083 includes configurable properties, flags, and/or lists that indicatehow event recognizers may interact with one another. In someembodiments, metadata 1083 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 1080 activates eventhandler 1090 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 1080 delivers event information associated with theevent to event handler 1090. Activating an event handler 1090 isdistinct from sending (and deferred sending) sub-events to a respectivehit view. In some embodiments, event recognizer 1080 throws a flagassociated with the recognized event, and event handler 1090 associatedwith the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 1088 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 1076 creates and updates data used inapplication 1036-1. For example, data updater 1076 updates the telephonenumber used in contacts module 1037, or stores a video file used invideo player module 1045. In some embodiments, object updater 1077creates and updates objects used in application 1036-1. For example,object updater 1076 creates a new user-interface object or updates theposition of a user-interface object. GUI updater 1078 updates the GUI.For example, GUI updater 1078 prepares display information and sends itto graphics module 1032 for display on a touch-sensitive display.

In some embodiments, event handler(s) 1090 includes or has access todata updater 1076, object updater 1077, and GUI updater 1078. In someembodiments, data updater 1076, object updater 1077, and GUI updater1078 are included in a single module of a respective application 1036-1or application view 1091. In other embodiments, they are included in twoor more software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 1000 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 11 illustrates a portable multifunction device 1000 having a touchscreen 1012 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (UI) 1200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making a gesture on the graphics, for example,with one or more fingers 1202 (not drawn to scale in the figure) or oneor more styluses 1203 (not drawn to scale in the figure). In someembodiments, selection of one or more graphics occurs when the userbreaks contact with the one or more graphics. In some embodiments, thegesture may include one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 1000. In some embodiments, inadvertentcontact with a graphic may not select the graphic. For example, a swipegesture that sweeps over an application icon may not select thecorresponding application when the gesture corresponding to selection isa tap.

Device 1000 may also include one or more physical buttons, such as“home” or menu button 1204. As described previously, menu button 1204may be used to navigate to any application 1036 in a set of applicationsthat may be executed on device 1000. Alternatively, in some embodiments,the menu button is implemented as a soft key in a GUI displayed on touchscreen 1012.

In one embodiment, device 1000 includes touch screen 1012, menu button1204, push button 1206 for powering the device on/off and locking thedevice, volume adjustment button(s) 1208, Subscriber Identity Module(SIM) card slot 1210, head set jack 1212, and docking/charging externalport 1024. Push button 1206 may be used to turn the power on/off on thedevice by depressing the button and holding the button in the depressedstate for a predefined time interval; to lock the device by depressingthe button and releasing the button before the predefined time intervalhas elapsed; and/or to unlock the device or initiate an unlock process.In an alternative embodiment, device 1000 also may accept verbal inputfor activation or deactivation of some functions through microphone1013.

It should be noted that, although many of the following examples will begiven with reference to inputs on touch screen 1012 (where the touchsensitive surface and the display are combined), a touch-sensitivesurface that is separate from the display may be used instead of touchscreen 1012.

Example Mapping Functionality

FIG. 12 illustrates another example of a multifunction device, which maybe configured in a manner similar to the multifunction device describedabove. In the illustrated embodiment, a multifunction device 1400includes a mapping application (e.g., map module 1054 described above)that may be stored in one or more memories of multifunction device 1400and executed on one or more processors of multifunction device 1400. Asis the case for the multifunction device described above, multifunctiondevice 1400 may include one or more controls 1402 for operating themultifunction device. These controls may include but are not limited topower controls for turning the device on and off, volume controls foradjusting the ear piece volume or the speaker volume, menu controls fornavigation functions of the device, and function controls for initiatingone or more function or actions on the device. Controls 1402 may includehardware controls or software controls. For instance, the bottom leftcorner of electronic display 1412 includes a graphical representation ofa control 1412 that may be selected by a user, such as by way of touchin accordance with the touch screen functionality described above.Multifunction device 1400 may also include other components similar tothose described above, such as a microphone 1404, an earpiece 1406(e.g., a speaker through which to convey audio representations oftelephone calls), an optical sensor 1408, and/or a speaker 1410. Each ofthese components may be configured in a similar manner to thoselike-named components of FIG. 11 described above. Furthermore,electronic display 1412 may be configured with touch screen capability,such as touch screen 1012 described above. In various embodiments,controls (e.g., on screen control(s) 1402) may be utilized to performany of a variety of map-related functions including but not limited tozoom in, zoom out, rotate screen, pan screen, toggle views (e.g.,two-dimensions to three dimensions and vice versa), and/or another maprelated activity. In various embodiments, one or more gestures may beutilized to perform any of the aforesaid map controls (with or withoutthe use of an actual graphical on-screen control). In one non-limitingexample, a one figure gesture may be utilized to adjust the pitch withina three-dimensional map view.

As noted above, multifunction device 1400 includes a mapping applicationthat may be stored in one or more memories of multifunction device 1400and executed on one or more processors of multifunction device 1400. Inthe illustrated embodiment, the graphical representation of the mappingapplication may include a map 1414 of a geographic region. This map maybe presented as a two-dimensional map or a three-dimensional map, theselection of which may be specified through, e.g., a user-configurableparameter of the mapping application. In some embodiments, themultifunction device may toggle between two-dimensional map orthree-dimensional map views responsive to input from any input componentof the multifunction device. In one non-limiting example, input fromorientation sensor(s) 1068 may initiate the transition from atwo-dimensional map view to a three-dimensional map, and vice versa. Forinstance, one or more of orientation sensor(s) 1068 may detect a tilt(e.g., a user-initiated tilt) in the orientation of the multifunctiondevice and, in response, initiate the aforesaid toggling.

Map 1414 may include a graphical position indicator 1416, which mayrepresent the location of the multifunction device within the geographicregion of the map. Generally position indicator 1416 may represent thecurrent or real-time position of the multifunction device, although itshould be understood that in some cases there may exist some smallamount of temporal latency between the actual position of themultifunction device and the graphical representation of that location(e.g., position indicator 1416). This may occur, e.g., when themultifunction device is in motion. In various embodiments, themultifunction device may be configured to perform map matching includingbut not limited to aligning a sequence of observed user positions with aroad network on a digital map. In various embodiments, the multifunctiondevice may be configured to perform a “snap to” function in which thegraphical position indicator 1416 is aligned onto a roadway when theuser's position falls within in a specified threshold distance of theroadway.

Furthermore, multifunction device 1400 may generally be operated by auser. For example, multifunction device 1400 may in some cases be asmartphone utilized by an individual to make phone calls, send textmessages, browse the internet, etc. As use of multifunction device by anindividual generally implies the individual is proximate to themultifunction device (e.g., the user may be holding the device in his orher hand), references herein to the location of the device and thelocation of the user may be considered to be synonymous. However, itshould be understood that in some cases the actual position of themultifunction device and the user of that device may differ by somedistance. For instance, the user may place his or her multifunctiondevice on a table of an outdoor café while sitting in a nearby chair. Inthis case, the position of the device and the position of the user maydiffer by some small amount. In another example, multifunction device1400 may be mounted on a car dashboard (e.g., for use as a navigationdevice) while the user of the device sits nearby (e.g., in the driverseat of the car). In this case as well, the position of the device andthe position of the user may differ by some small amount. Despite thesesmall differences in position, generally the position of themultifunction device and the position of the multifunction device usermay be considered to coincide.

In various embodiments, the map 1414 displayed by the multifunctiondevice may include one or more roads (e.g., roads 1418 a-b), buildings(not illustrated), terrain features (e.g., hills, mountains) (notillustrated), parks (not illustrated), water bodies (not illustrated),and/or any other item that may be conveyed by a map. In some cases, themap may also include other map or navigation information including butlimited to readouts from one or more of a directional compass, analtimeter, and/or a thermometer.

In various embodiments, the mapping application may be configured togenerate directions from an origination (e.g., an address or a user'scurrent position) to a destination (e.g., an address, landmark,bookmarked/saved location, or point of interest). For instance, anindication of the origination and/or destination may be input into themulti-function device by the user. The multifunction device may generateone or more candidate routes between those two points. The multifunctiondevice may select one of those routes for display on the device. Inother cases, multiple candidate routes may be presented to the user andthe user may select a preferred route. In the illustrated embodiment,one route is illustrated as route 1420. The route may also includeturn-by-turn directions which may be presented to the user (in 2D or3D), such as a graphical indication to perform a turn 1422 a from road1418 a to road 1418 b. In some embodiments, this graphical indication toperform a turn may be supplemented or substituted with an audibleindication to turn, such as a voice command from speaker 1410 thatindicates the user is to “turn left in 100 yards,” for example. In someembodiments, the route that is selected may be presented to the user asa route overview. For instance, before proceeding with navigation, themultifunction device may generate a route overview display thatgraphically indicates key information for the route, such as key turns,route distance and/or an estimated time for traversing the route. Insome cases, the multifunction device may be configured to generate adisplay of driving maneuvers (e.g., turns, lane changes, etc.) thatoccur in quick succession, either in the route overview or during actualnavigation. This information may help the user safely prepare for suchmaneuvers. In some cases, the route information may be presented in alist format, such as a list of turns or other maneuvers.

In various embodiments, the mapping application of the multifunctiondevice may be configured to track the position of the user over time andcorrespondingly adjust the graphical position indicator 1416 to indicatethe new position. For instance, the mapping application may determinethat the user is traveling along route 1420 from position information(e.g., information from GPS module 1035) and update the map 1414accordingly. For instance, in some cases the map 1414 may remainstationary while position indicator 1416 is moved along the route. Inother cases, position indicator 1416 may remain stationary or “fixed”while map 1414 is moved (e.g., panned, turned, etc.) around the positionindicator.

In various embodiments, the multifunction device may be configured todisplay alternate or contingency routes. In some cases, these routes maybe selectable by the user (e.g., via the touch screen interface). Inother cases, the multifunction device may select a best route based onone or more parameters, such as shortest distance or time. In somecases, these parameters or preferences may be set by the user.

As described in more detail below, the multifunction device may invarious embodiments receive routing information that specifies a routefrom a map service. In some case, the multifunction device may carry outnavigation guidance in accordance with this route. However, in somecases, the multifunction device may perform a reroute operation in orderto generate a new route to the destination. For instance, the user mayhave deviated from the original route or explicitly requested a newroute. In some cases, the multifunction device may perform reroutingbased on cached map data stored on the multifunction device.

In various embodiments, the multifunction device may be configured toperform route correction based on real-time data, such as updates in mapinformation, road conditions, traffic conditions, and/or weatherconditions. For instance, the multifunction device may be configured toalter a route such that the route avoids a construction zone or adangerous storm cell.

In various embodiments, the multifunction device may be configured toperform lane guidance independently or as part of navigation guidance.For instance, the multifunction device may, in response to detectingthat multiple turns follow in quick succession, provide the user with adirection or suggestion as to which lane to occupy. For instance, avoice or visual indication may specify that the user “turn right, thenmove to the left lane” in anticipation of a subsequent left turn. Inanother example, the multifunction device may detect one or more laneclosures (e.g., due to construction or other reasons) and instruct theuser to avoid such lanes.

In various embodiments, the multifunction device may be configured togenerate voice prompts for directions. For instance, during navigationguidance, the multifunction device may be configured to generate audiorepresentations of the next turn or driving maneuver on the route. Forinstance, the multifunction device may be configured to audibly indicatethe user should “turn left in 100 yards” or some other audibleindication of a maneuver.

In various embodiments, the multifunction device may be responsive tovarious voice commands for performing actions including a command toobtain a route. For instance, the multifunction device may interpret theuser's voice through a microphone or other transducer of themultifunction device. The user may specify an origination and adestination for the requested route. In various embodiments, themultifunction device may be configured to utilize the user's currentlocation as the origination for the route.

In various embodiments, the multifunction device may be configured toperform a search along a specific route, such as current navigationroute. For instance, the user of the multifunction device may requestthe location of points of interest, such as fuel stations orrestaurants. However, if a user is traveling along a particular route,they may not be particularly interested in points of interest that arenot proximate to that route. As such, the multifunction device may beconfigured to scope any searches to points of interested within aspecified distance away from the route. In various embodiments, thisdistance may be a configurable parameter.

In various embodiments, the multifunction device may be configured todisplay various graphical layers including but not limited to agraphical map information, aerial images (e.g., satellite-acquiredimages), and/or traffic information. For instance, in the trafficinformation example, the multifunction device may overlay color codedtraffic information on roadways to indicate the speed at which trafficis flowing. For example, green color coding may be used to indicatetraffic is flowing normally, and yellow or red may be used to indicatetraffic slowdowns.

In various embodiments, the multifunction device may be configured todisplay any quantity of metrics or statistics about a navigation routeincluding but not limited to an estimated time of arrival, traveldistance remaining, average speed (overall or moving average), topspeed, and/or other route statistics.

In various embodiments, the multifunction device may be configured todisplay routes at different angles in order to accommodate thepreferences of different users. Such viewing angles may include a bird'seye view for two-dimensional maps to any of a variety of camera anglesavailable for a three-dimensional map.

In various embodiments, the multifunction device may be configured toprovide navigation information other than map and routing information.For instance the multifunction device may expose output from any of thehardware device described above with respect to FIG. 9. In onenon-limiting example, an orientation sensor 1068 may include a compassthat outputs direction data. The multifunction device described hereinmay be configured to display this directional data as a virtual compass,for example.

Example System

Embodiments of the method for selectively obtaining map image dataaccording to virtual camera velocity as described herein may be executedon one or more computer systems such as the map service 130, which mayinteract with various other devices. One such computer system isillustrated by FIG. 13. In different embodiments, computer system 2000may be any of various types of devices, including, but not limited to, apersonal computer system, desktop computer, laptop, notebook, or netbookcomputer, mainframe computer system, handheld computer, workstation,network computer, a camera, a set top box, a mobile device, a consumerdevice, video game console, handheld video game device, applicationserver, storage device, a peripheral device such as a switch, modem,router, or in general any type of computing or electronic device.

In the illustrated embodiment, computer system 2000 includes one or moreprocessors 2010 coupled to a system memory 2020 via an input/output(I/O) interface 2030. Computer system 2000 further includes a networkinterface 2040 coupled to I/O interface 2030, and one or moreinput/output devices 2050, such as cursor control device 2060, keyboard2070, and display(s) 2080. In some embodiments, it is contemplated thatembodiments may be implemented using a single instance of computersystem 2000, while in other embodiments multiple such systems, ormultiple nodes making up computer system 2000, may be configured to hostdifferent portions or instances of embodiments. For example, in oneembodiment some elements may be implemented via one or more nodes ofcomputer system 2000 that are distinct from those nodes implementingother elements.

In various embodiments, computer system 2000 may be a uniprocessorsystem including one processor 2010, or a multiprocessor systemincluding several processors 2010 (e.g., two, four, eight, or anothersuitable number). Processors 2010 may be any suitable processor capableof executing instructions. For example, in various embodiments,processors 2010 may be general-purpose or embedded processorsimplementing any of a variety of instruction set architectures (ISAs),such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitableISA. In multiprocessor systems, each of processors 2010 may commonly,but not necessarily, implement the same ISA.

In some embodiments, at least one processor 2010 may be a graphicsprocessing unit. A graphics processing unit or GPU may be considered adedicated graphics-client device for a personal computer, workstation,game console or other computing or electronic device. Modern GPUs may bevery efficient at manipulating and displaying computer graphics, andtheir highly parallel structure may make them more effective thantypical CPUs for a range of complex graphical algorithms. For example, agraphics processor may implement a number of graphics primitiveoperations in a way that makes executing them much faster than drawingdirectly to the screen with a host central processing unit (CPU). Invarious embodiments, the image processing methods disclosed herein may,at least in part, be implemented by program instructions configured forexecution on one of, or parallel execution on two or more of, such GPUs.The GPU(s) may implement one or more application programmer interfaces(APIs) that permit programmers to invoke the functionality of theGPU(s). Suitable GPUs may be commercially available from vendors such asNVIDIA Corporation, ATI Technologies (AMD), and others.

System memory 2020 may be configured to store program instructionsand/or data accessible by processor 2010. In various embodiments, systemmemory 2020 may be implemented using any suitable memory technology,such as static random access memory (SRAM), synchronous dynamic RAM(SDRAM), nonvolatile/Flash-type memory, or any other type of memory. Inthe illustrated embodiment, program instructions and data implementingdesired functions, such as those described above for embodiments of themethod for rendering a map according to a stylesheet as described hereinare shown stored within system memory 2020 as program instructions 2025and data storage 2035, respectively. In other embodiments, programinstructions and/or data may be received, sent or stored upon differenttypes of computer-accessible media or on similar media separate fromsystem memory 2020 or computer system 2000. Generally speaking, acomputer-accessible medium may include storage media or memory mediasuch as magnetic or optical media, e.g., disk or CD/DVD-ROM coupled tocomputer system 2000 via I/O interface 2030. Program instructions anddata stored via a computer-accessible medium may be transmitted bytransmission media or signals such as electrical, electromagnetic, ordigital signals, which may be conveyed via a communication medium suchas a network and/or a wireless link, such as may be implemented vianetwork interface 2040.

In one embodiment, I/O interface 2030 may be configured to coordinateI/O traffic between processor 2010, system memory 2020, and anyperipheral devices in the device, including network interface 2040 orother peripheral interfaces, such as input/output devices 2050. In someembodiments, I/O interface 2030 may perform any necessary protocol,timing or other data transformations to convert data signals from onecomponent (e.g., system memory 2020) into a format suitable for use byanother component (e.g., processor 2010). In some embodiments, I/Ointerface 2030 may include support for devices attached through varioustypes of peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some embodiments, the function of I/Ointerface 2030 may be split into two or more separate components, suchas a north bridge and a south bridge, for example. In addition, in someembodiments some or all of the functionality of I/O interface 2030, suchas an interface to system memory 2020, may be incorporated directly intoprocessor 2010.

Network interface 2040 may be configured to allow data to be exchangedbetween computer system 2000 and other devices attached to a network,such as other computer systems, or between nodes of computer system2000. In various embodiments, network interface 2040 may supportcommunication via wired or wireless general data networks, such as anysuitable type of Ethernet network, for example; viatelecommunications/telephony networks such as analog voice networks ordigital fiber communications networks; via storage area networks such asFibre Channel SANs, or via any other suitable type of network and/orprotocol.

Input/output devices 2050 may, in some embodiments, include one or moredisplay terminals, keyboards, keypads, touchpads, scanning devices,voice or optical recognition devices, or any other devices suitable forentering or retrieving data by one or more computer system 2000.Multiple input/output devices 2050 may be present in computer system2000 or may be distributed on various nodes of computer system 2000. Insome embodiments, similar input/output devices may be separate fromcomputer system 2000 and may interact with one or more nodes of computersystem 2000 through a wired or wireless connection, such as over networkinterface 2040.

As shown in FIG. 13, memory 2020 may include program instructions 2025,configured to implement embodiments of the method for selectivelyobtaining map image data according to virtual camera velocity asdescribed herein, and data storage 2035, comprising various dataaccessible by program instructions 2025. In one embodiment, programinstructions 2025 may include software elements of embodiments of themethod selectively obtaining map image data according to virtual cameravelocity, as illustrated in FIG. 8. Data storage 2035 may include datathat may be used in embodiments. In other embodiments, other ordifferent software elements and data may be included.

Those skilled in the art will appreciate that computer system 2000 ismerely illustrative and is not intended to limit the scope of the methodfor rendering a map according to a stylesheet as described herein. Inparticular, the computer system and devices may include any combinationof hardware or software that can perform the indicated functions,including a computer, personal computer system, desktop computer,laptop, notebook, or netbook computer, mainframe computer system,handheld computer, workstation, network computer, a camera, a set topbox, a mobile device, network device, internet appliance, PDA, wirelessphones, pagers, a consumer device, video game console, handheld videogame device, application server, storage device, a peripheral devicesuch as a switch, modem, router, or in general any type of computing orelectronic device. Computer system 2000 may also be connected to otherdevices that are not illustrated, or instead may operate as astand-alone system. In addition, the functionality provided by theillustrated components may in some embodiments be combined in fewercomponents or distributed in additional components. Similarly, in someembodiments, the functionality of some of the illustrated components maynot be provided and/or other additional functionality may be available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or on storage while beingused, these items or portions of them may be transferred between memoryand other storage devices for purposes of memory management and dataintegrity. Alternatively, in other embodiments some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated computer system via inter-computercommunication. Some or all of the system components or data structuresmay also be stored (e.g., as instructions or structured data) on acomputer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described above. Insome embodiments, instructions stored on a computer-accessible mediumseparate from computer system 2000 may be transmitted to computer system2000 via transmission media or signals such as electrical,electromagnetic, or digital signals, conveyed via a communication mediumsuch as a network and/or a wireless link. Various embodiments mayfurther include receiving, sending or storing instructions and/or dataimplemented in accordance with the foregoing description upon acomputer-accessible medium. Accordingly, the present invention may bepracticed with other computer system configurations.

What is claimed is:
 1. A method, comprising: performing, by a computing device implementing a map application, wherein said map application displays a map view of a map, wherein said map view is displayed based on preexistent map image data identified according to a virtual camera, comprising: detecting a velocity of the virtual camera; selecting the preexistent map image data for the map view of the map corresponding to a particular level-of-detail, wherein the particular level-of-detail is one of a plurality of levels-of-detail each corresponding to different respective map image data previously generated for the map view of a same area of the map, wherein the particular level-of-detail is determined according to the velocity of the virtual camera; and obtaining the selected preexistent map image data.
 2. The method of claim 1, wherein said detecting the velocity of the virtual camera comprises determining a velocity of a rotation of the virtual camera in a fixed position.
 3. The method of claim 1, wherein said selecting the preexistent map image data for the map view of the map corresponding to the particular level-of-detail comprises: determining whether the detected velocity exceeds a velocity threshold; and in response to determining that the detected velocity exceeds a velocity threshold, specifying the particular level-of-detail for the map image data.
 4. The method of claim 3, wherein said specifying the particular level-of-detail for the preexistent map image data comprises selecting the particular level-of-detail for the preexistent map image data according to a distance from the virtual camera to a location of the map image data in a virtual space.
 5. The method of claim 1, wherein the map image data is obtained from a server.
 6. The method of claim 1, wherein the preexistent map image data is obtained from accessing map image data stored at the computing device.
 7. The method of claim 1, further comprising: determining whether all of the selected preexistent map image data for the map view of the map according to the velocity of the virtual camera is obtained; and in response to determining all of the selected preexistent map image data for the map view map according to the velocity of the virtual camera is obtained: obtaining different preexistent map image data corresponding to a different level-of-detail of the plurality of levels-of detail that is determined independent of the detected velocity of the virtual camera.
 8. A system, comprising: at least one processor; and a memory comprising program instructions, wherein the program instructions implement a map application, wherein said map application displays a map view of a map, wherein said map view is displayed based on preexistent map image data identified according to a virtual camera, executable by the at least one processor to: detect a velocity of the virtual camera; select the preexistent map image data for the map view of the map corresponding to a particular level-of-detail, wherein the particular level-of-detail is one of a plurality of levels-of-detail each corresponding to different respective map image data previously generated for the map view of a same area of the map wherein the particular level-of-detail is determined according to the velocity of the virtual camera; and obtain the selected preexistent map image data.
 9. The system of claim 8, wherein, to detect the velocity of the virtual camera, the program instructions are executable by the at least one processor to analyze input from one or more orientation sensors that move the virtual camera.
 10. The system of claim 8, wherein, to detect the velocity of the virtual camera, the program instructions are executable by the at least one processor to analyze input from a touch-enabled input device that manipulates the virtual camera.
 11. The system of claim 8, wherein, to select the preexistent map image data for the map view of the map corresponding to the particular level-of-detail, the program instructions implement a map application executable by the at least one processor to: determine whether the detected velocity exceeds a velocity threshold; and in response to determining that the detected velocity exceeds a velocity threshold, specify the level-of-detail for the map image data.
 12. The system of claim 8, wherein the preexistent map image data obtained comprises two or more areas, wherein at least one of said two or more areas comprises vector graphics data, and wherein at least one other of said two or more areas comprises raster graphics data.
 13. A non-transitory computer-readable storage medium, storing program instructions, wherein the program instructions when executed by one or more computing devices cause the one or more computing devices to implement a map application, wherein the map application displays a map view of a map, wherein the map view is displayed based on preexistent map image data identified according to a virtual camera, and wherein the map application implements: detecting a velocity of the virtual camera; selecting the preexistent map image data for the map view of the map corresponding to a particular level-of-detail, wherein the particular level-of-detail is one of a plurality of levels-of-detail each corresponding to different respective map image data previously generated for the map view of a same area of the map, wherein the particular level-of-detail is determined according to the velocity of the virtual camera; and obtaining the selected preexistent map image data.
 14. The non-transitory, computer-readable storage medium of claim 13, wherein, in said detecting the velocity of the virtual camera, the map application implements determining a velocity of a rotation of the virtual camera in a fixed position.
 15. The non-transitory, computer-readable storage medium of claim 13, wherein, in said selecting the preexistent map image data for the map view of the map corresponding to the particular level-of-detail, the map application implements: determining whether the detected velocity exceeds a velocity threshold; and in response to determining that the detected velocity exceeds a velocity threshold, specifying the particular level-of-detail for the preexistent map image data.
 16. The non-transitory, computer-readable storage medium of claim 15, wherein in said specifying the particular level-of-detail for the preexistent map image data, the map application implements selecting the particular level-of-detail for the preexistent map image data according to a distance from the virtual camera to a location of the map image data in a virtual space.
 17. The non-transitory, computer-readable storage medium of claim 13, wherein the obtained map image data comprises one or more map tiles, wherein at least one of the one or more map tiles comprises two or more areas, wherein at least one of said two or more areas comprises vector graphics data, and wherein at least one other of said two or more areas comprises raster graphics data.
 18. An electronic navigation device, comprising: an electronic display; a navigation component, wherein said navigation component displays a navigation view of a map, wherein said navigation view is displayed according to a virtual camera, configured to: detect a velocity of the virtual camera; select preexistent map image data for the navigation view of the map corresponding to a particular level-of-detail according to the velocity of the virtual camera, wherein the particular level-of-detail is one of a plurality of levels-of-detail each corresponding to different respective map image data previously generated for the map view of a same area of the map, wherein the selection comprises: determine whether the detected velocity exceeds a velocity threshold; and in response to a determination that the detected velocity exceeds a velocity threshold, specify the particular level-of-detail for the preexistent map image data; obtain the selected preexistent map image data; and display the obtained preexistent map image data.
 19. The device of claim 18, further comprising: a positioning component configured to determine a current location of the electronic navigation device; wherein, to determine whether the detected velocity exceeds the velocity threshold, the navigation component is configured to analyze location data obtained from the position component.
 20. The system of claim 18, wherein, to specify the particular level-of-detail for the preexistent map image data, the navigation component is configured to select the particular level-of-detail for the map image data according to a distance from the virtual camera to a location of the map image data in a virtual space.
 21. A multi-function device, comprising: a touch-sensitive display; at least one processor; and a memory comprising program instructions, wherein the program instructions cause the at least one processor to implement a map application, wherein the map application displays a map view of a map, wherein the map view is displayed based on preexistent map image data identified according to a virtual camera, and wherein the map application is configured to: detect a velocity of the virtual camera; select the preexistent map image data for the navigation view of the map corresponding to a particular level-of detail according to the velocity of the virtual camera, wherein the particular level-of-detail is one of a plurality of levels-of-detail each corresponding to different respective map image data previously generated for the map view of a same area of the map, the selection, wherein the selection comprises: determine whether the detected velocity exceeds a velocity threshold; and in response to a determination that the detected velocity exceeds a velocity threshold, specify the particular level-of-detail for the preexistent map image data; obtain the selected preexistent map image data; and display the obtained preexistent map image data on the touch-sensitive display.
 22. The device of claim 21, wherein, to detect the velocity of the virtual camera, the map application is configured to analyze touch input obtained via the touch-sensitive display to determine the virtual camera velocity.
 23. The device of claim 21, further comprising: one or more orientation sensors; wherein, to detect the velocity of the virtual camera, the map application is configured to analyze the one or more orientation sensors to determine the virtual camera velocity.
 24. The device of claim 21, wherein, to specify the particular level-of-detail for the preexistent map image data, the map application is configured to select the particular level-of-detail for the preexistent map image data according to a distance from the virtual camera to a location of the map image data in a virtual space.
 25. The device of claim 21, wherein the obtained map image data is obtained from the device memory. 